Bug description

• File Selection is removed after opening any dialog in the File manager for performing any file operation.
• Selected items are not id values in File manager instead name values are added.
• Delete operation is not working
• The search operation is not returning the CWD value so file operations are not working properly
• File Manager path is not created based on path ids instead created with the name
• Rename a file/folder in a subfolder/ nested folder to the root folder, the application stops.
• Breadcrumb navigation application stops.
• After cut copy paste selection is not maintained.
• Right-clicking on a file or folder after selecting it, selection removed.
• Delete a file/folder in a subfolder/ nested folder to the root folder, the application stops.

Root cause

Since the Id based handling is not included in the File manager component, these issues occurred, I have now provided changes for handling id-based services to resolve this issue.

Solution description

I have made changes to support for the Id based file provider services to make sure all the operations are working in the Blazor file manager component.

Reason for not identifying earlier

• Guidelines not followed. If yes, provide which guideline is not followed.

• Guidelines not given. If yes, provide which/who need to address.
  Tag label update-guideline-coreteam or update-guideline-productteam.

• If any other reason, provide the details here - Since id service handling is not provided in the File manager component, these issues occur.

Areas tested against this fix

Provide details about the areas or combinations that have been tested against this code changes.

• Tested against feature matrix. Feature matrix link

Is it a breaking issue?

• Yes, Tag breaking-issue.
• NO

If yes, provide the breaking commit details / MR here.

Action taken

We have fixed all the issue in the SQL file service provider in the Blazor File manager component

Feature matrix document updated

• Yes
• NO
• NA

Automation details - Mark Is Automated field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the bug is automated.

• BUnit, share corresponding MR.
• E2E or Manual Automation using tester - Make sure all items are automated with priority before release which can be tracked in automation dashboard.

If the same issue is reproduced in ej2, what will you do?

• Resolved. Provide MR link.
• NO. Created task to track it. Share task link.
• NA

Is this common issue need to be addressed in the same component or on other components in our platform?

• Yes - Need to check in other components, tag needs-attention-coreteam
• No

Output screenshots

NA

Blazor Checklist

Confirm whether this feature is ensured in both Blazor Server and WASM

• NA
• Yes
• NO

Is there any new API or existing API name change?

• Yes. If yes, Provide API Review task link.
• NO

Is there any existing behavior change due to this code change?

• Yes. Add breaking-change label.
• NO

Do the code changes cause any memory leak and performance issue? (Test only if you suspect that your code may cause problem)

• Yes
• NO

Reviewer Checklist

• All provided information are reviewed and ensured.